System and method for variable block logging with log-ahead buffers

ABSTRACT

A system for logging database transactions comprises a memory (comprising a direct access storage device) operable to store a database, a database log, and a plurality of log buffers associated with the database log. Each log buffer is operable to store at least one log record associated with a database transaction. The system further comprises a processor operable to log a first record of a first database transaction using the database log and write the database log to the storage device. The processor is further operable to log a second record of a second database transaction in a first of the plurality of log buffers substantially concurrently to the database log being written to the storage device.

RELATED APPLICATION

This application claims the priority under 35 U.S.C. §119 of provisional application Ser. No. 60/601,378 filed Aug. 13, 2004.

TECHNICAL FIELD

This disclosure generally relates to database management and, more specifically, to a system and method for variable block logging with log-ahead buffers.

BACKGROUND

Relational database management systems (RDBMSS) may utilize an active transaction log file (also referred to as a “transaction journal” or “journal file”) or similar facility to record updates done by a transaction to provide transaction integrity and recoverability. This information is also used when the database system fails for some reason and the system needs to be restarted and restored to a “stable state”. Typically this stable state means the most recent point where all complete (committed) updates have been written to the database and any in-flight updates (uncommitted) are removed from the database. Conventional database logs use a fixed-block architecture to store the transaction logs that represent the updates made by the transactions. The fixed-block architecture allows the current log buffer to be rewritten to the same log block multiple times (as needed) to ensure that transaction updates that have been committed are recorded on the physical log file DASD (direct access storage device) before the actual transaction is allowed to commit or complete. In a typical environment a log buffer may be re-written to the log file DASD multiple times. Such writes to the DASD may be triggered, for example, when certain events take place (such as “commits” saving changes in the database), at certain time intervals, when the log buffer is full, or based on other predetermined or dynamic determined conditions. While the log buffer is being written to the log file DASD, other tasks that need to record transaction information in the log buffer or log file may be held until the DASD write is completed, which may introduce delays in transaction processing.

SUMMARY

This disclosure provides a system and method for using a variable format log buffer and log block (DASD file) for logging database transactions. Included in this system and method is memory (including a direct access storage device) operable to store a database, a database log, and a plurality of log buffers associated with the database log. Each log buffer is operable to store at least one log record associated with a database transaction. The system further comprises a processor operable to log a first record of a first database transaction using the database log and write the database log to the storage device. The processor is further operable to log a second record of a second database transaction in a first of the plurality of log buffers substantially concurrently to the database log being written to the storage device.

In another example embodiment, software for logging database transactions is operable to log a first record of a first database transaction using a database log and write the database log to a storage device. The software is further operable to log a second record of a second database transaction in a first log buffer substantially concurrently to the database log being written to the storage device. The details of one or more embodiments of the disclosure are set forth in the accompanying drawings and the description below. Particular features, objects, and advantages of the disclosure will be apparent from the description and drawings and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an environment implementing database logging using multiple log buffers; and

FIG. 2 is a flow chart illustrating an example method of database logging using multiple log buffers.

DETAILED DESCRIPTION

FIG. 1 illustrates a relational database environment 100 for storing and retrieving information in at least a portion of enterprise or data processing environment in accordance with a particular implementation of a system and method for using variable logging to record transaction information for a database 130. Generally, environment 100 allows for variable logging of database 130 by using log-ahead buffers. With variable logging, log records are added to a current log buffer (or a first log buffer with space) that is not written until the buffer is full or an event occurs that requests that the buffer be on disk. In this case, the write is often the length of data currently in the buffer. In other words, environment 100 maintains log files for database 130 using multiple log buffers 140, which may allow various processes to take place concurrently with log files being written to a direct access storage device (DASD) or memory 120. Memory 120 may be physically or logically separate from server 102 to provide additional protection against possible causes of server failure 102. As described in more detail below, memory 120 includes physical blocks, which may be written wholly or partially during a particular write operation. Certain embodiments also provide for fixed logging, in which log buffers 140 have a fixed length corresponding to a block size on memory 120, while other embodiments (alternatively or in combination) use variable logging, allowing log buffers 140 to have a variable length up to a maximum capacity. In other words, in certain embodiments, environment 100 may fill log records left to right in log buffer 140 a, issue an I/O whenever a “first” commit is received, and dynamically store other tasks' log records in other log buffers 140 b and 140 c. In this example, multiple tasks can be simultaneously filling log buffers 140. The term “dynamically,” as used herein, generally means that certain processing is determined, at least in part, at run-time based on one or more variables. The term “automatically,” as used herein, generally means that the appropriate processing is substantially performed by at least part of distributed application environment 100. It should be understood that “automatically” further contemplates any suitable administrator or other user interaction with environment 100 without departing from the scope of this disclosure.

Returning to the illustrated embodiment, environment 100 may be a distributed client/server system that allows users of clients 104 to submit requests to store or modify and/or retrieve information from database 130, which is maintained on illustrated server 102 (but may reside elsewhere to be managed by server 102, such as in a data warehouse or repository). But environment 100 may also be a standalone computing environment or any other suitable environment, such as an administrator or data manager accessing data stored on server 102, without departing from the scope of this disclosure. Environment 100 may allow access to database 130 using a structured query language (SQL) or other suitable or generic database query language (XML). Database 130 is typically a relational database that uses sets of schemas to describe the tables, columns, and relationships in the tables using basic principles known in the field of database design. But, while described in relational terms, in other embodiments, database 130 may comprise XML documents, flat files, Btrieve files, or comma-separated-value (CSV) files. As database 130 is being managed by server 102, it may be desirable to maintain an active log file (or “journal”) 106 documenting “transactions,” which generally include any access, change, or command to database 130. Log file 106 may be local or remote, as well as distributed, without departing from the scope of the disclosure. In certain embodiments, whether the transaction is to be logged may be determined by the administrator or system resources or security. Database 130, normally though database manager 135 (described below), tracks operations in a particular log file 106 that is segmented into or supplemented with a plurality of log buffers 140. Log records are added to log file 106 or to a particular log buffer 140 as various database operations are performed. Various embodiments of environment 100 provide for multiple log buffers 140 allowing log records to be buffered while one or more log buffers 140 are being written to memory 120. For example, free or newly activated log buffers 140 can store log records while the contents of other full or to-be-written log buffers 140 are being written to memory 120. This may allow additional transactions to take place while memory 120 is being written to DASD, allowing for greater concurrency in database 130. Moreover, having additional log buffers 140 reduces the chance that all log buffers 140 will be full when a transaction is about to take place, which could require the transaction to be held while log buffer 140 is written to the database. For example, enough buffers 140 may exist so that the time during a write is matched by the number of buffers available. The number and/or size of log buffers 140 may be selected by a user or determined automatically and/or dynamically based on system requirements in order to take advantage of increased performance while limiting the amount of system resources required for log buffers 140. For example, database 130 may allow the user to select between a range of buffers 140, such as between four and ninety-nine. In another example, the number and/or size of log buffers 140 may default to eight and then be determined dynamically based on system usage, so that when usage is relatively high, more or larger buffers 140 are used. In certain embodiments, the write of one log buffer to memory 120 will look at the other log buffers (with active transaction data) to see if more than one log buffer can be written with a single write request. This may save the number of writes as well as processing time. In this example, a maximum of a six log buffers 140 may be written as one request using chained input/output (I/O). This example six buffer write normally represents three tracks (of 3390 DASD). If fewer buffers 140 are available to be written, then as few as a single buffer 140 will be written. Writes to memory 120 are normally performed when a particular log buffer 140 is full or when an event that requires a log buffer 140 to be committed is detected. For example, a “commit” event which saves changes to database 130 could prompt buffered log entries to be saved to DASD 139. During the write to memory 120, additional records may be written to the physical block being written if log buffer 140 is not full. But once a number of log records sufficient to fill log buffer 140 are being written to the physical block, log records for transactions may be sent to another log buffer 140 while the write of current log buffer 140 to memory 120 is being performed, which increases the number of transactions that can be performed simultaneously in the database (also known as “concurrency”). A particular log buffer 140 that is not full is typically not written unless it is requested to be on memory 120 by the event. In certain embodiments, log current buffer writes will be done without waiting on completion for normal maintenance commands. In this case, it may allow more overlap of processing during the log write. Commands that require completion, such as commit commands, may wait for completion as necessary. Other advantages of particular embodiments are described herein or may be understood by those skilled in the art. Of course, particular embodiments may have some, all, or none of the enumerated advantages.

Server 102 includes memory 120 and processor 125 and comprises an electronic computing device operable to receive, transmit, process and store data associated with environment 100. For example, server 102 may be any computer or processing device such as a mainframe, a blade server, general-purpose personal computer (PC), Macintosh, workstation, Unix-based computer, or any other suitable device. Generally, FIG. 1 provides merely one example of computers that may be used with the disclosure. In other words, the present disclosure contemplates computers other than general purpose computers as well as computers without conventional operating systems. As used in this document, the term “computer” is intended to encompass a personal computer, workstation, network computer, or any other suitable processing device. For example, although FIG. 1 illustrates one server 102 that may be used with the disclosure, environment 100 can be implemented using computers other than servers, as well as a server pool. Server 102 may be adapted to execute any operating system including z/OS, Linux-Intel or Linux/390, UNIX, Windows Server, or any other suitable operating system. According to one embodiment, server 102 may also include or be communicably coupled with a web server and/or an SMTP server.

Memory 120 may include any memory or database module and may take the form of volatile or non-volatile memory including, without limitation, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), removable media, or any other suitable local or remote memory component. In certain embodiments, at lease a portion of memory 120 is a DASD 139. Illustrated memory 120 also includes database 130, log buffers 140 comprising or added to log file 106, force area 145, database manager 135, which may be any set of logical instructions executed by processor 125 to perform tasks associated with database management and/or responding to queries, including storing information in memory 120, searching database 130, generating responses to queries using information in database 130, restoring portions of database 130 from backup records 106, and numerous other related tasks. In particular, database manager 135 manages generated or received log records, storing log records in log buffers 140, and requesting or managing the write the contents of log buffers 140 to DASD 139. In certain embodiments, database manager 135 may collect, generate, or format statistics involving buffers 140. For example, the first statistical count may represent the number of times the first log buffer 140 is activated. This example count normally occurs when the current buffer 140 in log file 106 is full and no other log buffers 140 are in use. If activated, buffer 140 may include only one record or a full block of records before it is written. A similar count is provided for log buffers 2-nn. For example, certain embodiments may use up to 99 log buffers 140, but any number of buffers 140 may be used up to the availability of memory. The next example statistical counter is the count of times that certain log buffers 140 are full and a transaction wait should occur for a current write to free one or more log buffers 140. If this count is large, the administrator or a component may want to increase the number of log buffers 140. Yet more example statistical counters provide the grouping of multiple log buffers 140 into a single write to DASD 139. The first counter provides for the times that two log buffers 140 are written with a single write. Additional example counts may be provided for writing three buffers, four buffers, five buffers, or six buffers. In general, two buffers often fit per DASD track and so, in these cases, this write of six buffers would represent three tracks of log data.

Database manager 135 is typically software and may be written or described in any appropriate computer language including, for example, C, C++, Java, J#, Visual Basic, assembler, Perl, any suitable version of 4GL, or any combination thereof. As used herein, software generally includes any appropriate combination of software, firmware, hardware, and/or other logic. It will be understood that while database manager 135 is illustrated in FIG. 1 as a single multi-tasked module, the features and functionality performed by this engine may be performed by multiple modules such as, for example, one or more agents or database instances. Further, while illustrated as internal to server 102, one or more processes associated with database manager 135 may be stored, referenced, or executed remotely—in one embodiment, database manager 135 may be referenced by or communicably coupled with applications executing on client 104. Moreover, database manager 135 may be a child or sub-module of another software module (not illustrated) without departing from the scope of this disclosure—indeed database manager 135 and database 130 may comprise the same or child/parent modules without departing from the scope of the disclosure.

Particular embodiments of memory 120 may also include a “force area” file 145 to handle overflows from log file 106 when information needs to be written or recovered (known as a “forced transaction”) while log file 106 is currently occupied. Force area 145 may have a block size set to match that of log file 106. Alternatively, if the size of log file 106 is set to be exceptionally large for variable logging applications, Force area 145 may use a smaller block size that would be suitable for handling writes to log file 106, such as the maximum size of log buffers 140.

Server 102 also includes processor 125. Processor 125 executes instructions and manipulates data to perform the operations of server 102 such as, for example, a central processing unit (CPU), a blade, an application specific integrated circuit (ASIC), or a field-programmable gate array (FPGA). In particular, processor 125 performs any suitable tasks associated with or requested by database manager 135, including the creation, use, and freeing of log buffers 140, as well as writing the contents of log buffers 140 to DASD. Although FIG. 1 illustrates a single processor 125 in server 102, multiple processors 125 may be used according to particular needs and reference to processor 125 is meant to include multiple processors 125 where applicable.

Server 102 may also include interface 117 for communicating with other computer systems, such as client 104, over network 112 in a client-server or other distributed environment. In certain embodiments, server 102 receives queries from local or remote senders through interface 117 for storage in memory 120 and/or processing by processor 125. Generally, interface 117 comprises logic encoded in software and/or hardware in a suitable combination and operable to communicate with network 112. More specifically, interface 117 may comprise software supporting one or more communications protocols associated with communications network 112 or hardware operable to communicate physical signals.

Network 112 facilitates wireless or wireline communication between computer server 102 and any other local or remote computer, such as clients 104. Indeed, while illustrated as two networks, 112 a and 112 b respectively, network 112 may be a continuous network without departing from the scope of this disclosure, so long as at least portion of network 112 may facilitate communications between senders and recipients of queries and results. In other words, network 112 encompasses any internal and/or external network, networks, sub-network, or combination thereof operable to facilitate communications between various computing components in environment 100. Network 112 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses. Network 112 may include one or more local area networks (LANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global computer network known as the Internet, and/or any other communication system or systems at one or more locations.

Client 104 is any local or remote computing device operable to receive requests from the user via a user interface 116, such as a GUI, a CLI (Command Line Interface), or any of numerous other user interfaces. Thus, where reference is made to a particular interface, it should be understood that any other user interface may be substituted in its place. In various embodiments, each client 104 includes at least GUI 116 and comprises an electronic computing device operable to receive, transmit, process and store any appropriate data associated with environment 100. It will be understood that there may be any number of clients 104 communicably coupled to server 102. For example, illustrated clients 104 include one local client 104 and two clients external to the illustrated portion of enterprise 100. Further, “client 104” and “user” may be used interchangeably as appropriate without departing from the scope of this disclosure. Moreover, for ease of illustration, each client 104 is described in terms of being used by one user. But this disclosure contemplates that many users may use one computer or that one user may use multiple computers to submit or review queries via GUI 116. As used in this disclosure, client 104 is intended to encompass a personal computer, touch screen terminal, workstation, network computer, kiosk, wireless data port, wireless or wireline phone, personal data assistant (PDA), one or more processors within these or other devices, or any other suitable processing device. For example, client 104 may comprise a computer that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information, and an output device that conveys information associated with the operation of server 102 or clients 104, including digital data, visual information, or GUI 116. Both the input device and output device may include fixed or removable storage media such as a magnetic computer disk, CD-ROM, or other suitable media to both receive input from and provide output to users of clients 104 through the display, namely GUI 116.

GUI 116 comprises a graphical user interface operable to allow the user of client 104 to interface with at least a portion of environment 100 for any suitable purpose. Generally, GUI 116 provides the user of client 104 with an efficient and user-friendly presentation of data provided by or communicated within environment 100. For example, GUI 116 may be a front-end of an application executing on client 104 that is operable to submit SQL queries to database 130. GUI 116 may comprise a plurality of customizable frames or views having interactive fields, pull-down lists, and buttons operated by the user. In one embodiment, GUI 116 presents information associated with queries and buttons and receives commands from the user of client 104 via one of the input devices. Moreover, it should be understood that the term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, GUI 116 contemplates any graphical user interface, such as a generic web browser or touch screen, that processes information in environment 100 and efficiently presents the results to the user. Server 102 can accept data from client 104 via the web browser (e.g., Microsoft Internet Explorer or Netscape Navigator) and return the appropriate HTML or XML responses using network 112. For example, server 102 may receive such an SQL query from client 104 using the web browser and then execute the parsed query to store and/or retrieve information in database 130.

In operation, log buffers 140 are used to store log records of database transactions as they occur. Server 102 monitors activity in log buffers 140 to determine when information needs to be written to memory 120, specifically storage device 139. For example, certain events, such as transactions issuing a commit request, may trigger a write to DASD 139. Also, log buffers 140 may be written as they become full. When a need to write to DASD 139 arises, server 102 (typically via example database manager 135) initiates the write. During the write, new log records may be stored in new or activated log buffers 140 and additional records may even be written as part of the write of log buffer 140. For example, if the particular log buffer 140 being written is not filled to the size of a track on DASD, then remaining space on the track may be filled during the same write operation using records from other log buffers 140 or new log records being received during the write. This may advantageously reduce the number of writes to DASD 139, thus conserving system resources, such as processing resources. So long as there is available log buffer 140 space available, logged database operation may continue. Occasionally, all log buffers 140 may be filled, which may require transactions requiring log space to be held. Similarly, there may be times when a second request triggering a write to DASD 139 will be received while another write is taking place, which may require transactions to be held. But the use of multiple log buffers 140 may significantly reduce the number of times that transactions must be held, improving system concurrency and user availability.

FIG. 2 is a flow chart illustrating an example method 300 for logging database transactions using multiple log buffers 140. Method 300 is described in respect to system 100 and, more specifically, to database manager 135. However, any other suitable system, server, or software may use or implement method 300 or other analogous technique to dynamically log transactions without departing from the scope of this disclosure.

In illustrated method 300, server 102 receives or executes a particular database transaction at step 302. As described above, this task may be any logged, audited, or to-be committed transaction including, for example, a query, a command, a security or administrative task, a command line entry, or any other suitable communication that may be logged or committed to memory 120. At step 304, database manager 135 stores one or more log records for the particular transaction in a first log buffer 140 a of log file 106 as appropriate. Database manager 135 continues to receive log records and store them in log buffer 140 a until a write to memory 120 (or its component DASD 139) is appropriate or efficacious, as shown by step 306. This write may be performed because a particular task requires a write to memory 120, because one or more log buffers 140 are full, or for any other reason for which a write or commit to DASD 139 may be useful. For example, database manager 135 determines if the current log file 106 or log buffer 140 a is full at decisional step 308. If the current buffer 140 a is not full, then database manager 135 detects whether the transaction is a commit or other triggering event, such as a task requiring a write to DASD 139, is received, as shown by decisional step 310. When a write is to be performed, database manager 135 begins the write to DASD 139 at step 314. In certain embodiments, if an additional trigger is received, database manager 135 holds this write task at step 312 until the current write to DASD 139 is completed. Regardless, during the write, database manager 135 may receive information associated with another database transaction, as indicated at step 312. If tasks are not being held for an additional trigger, then database manager 135 may determine whether additional space in one of the log buffers 140 is available. If additional space is available for logging, then database manager 135 activates the next log buffer 140 b (often in sequence from left to right) at step 316. The additional received transactions are then stored in the now active log buffer 140 b at step 318. Database manager 135 continues to receive or generate log records and store them in the second log buffer 140 b until a write to memory 120 is appropriate or efficacious.

Returning to the first log buffer 140 a, if the write of the current log buffer 140 a is not complete at decisional step 320, execution proceeds to step 324, where database manager 135 continues writing the current log buffer 140 a, monitoring for additional triggers or filled buffer capacity that may require tasks to be held. Once the write of the current log buffer 140 a is complete, database manager 135 may clear or free all or part of that log buffer 140 a at step 322.

While not illustrated, database manager 135 may then determine whether additional buffers may be written to DASD 139 in the current write operation. For example, if there is space left on a track being written, database manager 135 may write additional records from other log buffers 140 up to the end of the track. If additional log buffers 140 may be written, database manager 135 begins writing the next log buffer 140 to DASD 139. In this case, the next log buffer 140 is written in the same manner as described above. If there are no additional buffers to be written, then server 102 may determine whether another write to DASD is required. For example, if server 102 received an additional trigger requiring a write to DASD while the previous write was being performed, then the write for the next task may be performed. In such a case, execution would return to step 308, for example, thereby beginning a new write operation. Otherwise, server 102 may repeat some or all of the described techniques, such as from step 302, until database operation is interrupted.

The preceding flow chart presents an example method 300 for logging using multiple log buffers 140, but numerous other similar or distinct methods could be employed or implemented as well. In particular, any method of operation suitable for use with any of the embodiments of environment 100 described herein is contemplated within this disclosure. Accordingly, many of the steps in this flowchart may take place simultaneously and/or in different orders than as shown. Moreover, environment 100 may use methods with additional steps, fewer steps, and/or different steps, so long as the methods are consistent with any of the techniques for logging using multiple log buffers 140 described or suggested herein.

Although this disclosure has been described in terms of certain embodiments and generally associated methods, alterations and permutations of these embodiments and methods will be apparent to those skilled in the art. For example, different methods of determining when to write to DASD, how to determine which log buffers 140 are written, and numerous other possible variations are contemplated within the scope of this disclosure. Accordingly, the above description of example embodiments does not constrain the scope of the claims. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure. 

1. A method for logging database transactions, comprising: logging a first record of a first database transaction using a database log; writing at least a portion of the database log to a storage device; and logging a second record of a second database transaction in a first log buffer substantially concurrently to the database log being written to the storage device.
 2. The method of claim 1, further comprising: receiving information associated with a third database transaction; and in response to the first log buffer being full, logging a third record of the third database transaction in a second log buffer substantially concurrently to the database log being written to the storage device.
 3. The method of claim 2, upon completion of the write of the database log to the storage device, the method further comprising: receiving information associated with a fourth database transaction; logging a fourth record of the fourth database transaction in the database log; and writing the first and second log buffers to the storage device using chained input/output.
 4. The method of claim 3, upon completion of the write of the first and second log buffers to the storage device, the method further comprising freeing the first and second log buffers.
 5. The method of claim 1, further comprising writing the database log to the storage device in response to detecting a trigger event.
 6. The method of claim 1, further comprising: receiving information associated with a third database transaction; in response to the third transaction comprising a triggering event, logging a third record of a fourth database transaction in a second log buffer substantially concurrently to the database log being written to the storage device; and writing the first log buffer to the storage device up upon completion of the write of the database log to the storage device.
 7. The method of claim 1, wherein a total number of log buffers and a size for each of the log buffers is dynamically determined based on system usage.
 8. Software for logging database transactions, the software operable when executed to: log a first record of a first database transaction using a database log; write at least a portion of the database log to a storage device; and log a second record of a second database transaction in a first log buffer substantially concurrently to the database log being written to the storage device.
 9. The software of claim 8, further operable to: receive information associated with a third database transaction; and in response to the first log buffer being full, log a third record of the third database transaction in a second log buffer substantially concurrently to the database log being written to the storage device.
 10. The software of claim 9, upon completion of the write of the database log to the storage device, the software further operable to: receive information associated with a fourth database transaction; log a fourth record of the fourth database transaction in the database log; and write the first and second log buffers to the storage device using chained input/output.
 11. The software of claim 10, upon completion of the write of the first and second log buffers to the storage device, the software further operable to free the first and second log buffers.
 12. The software of claim 8, further operable to write the database log to the storage device in response to detecting a trigger event.
 13. The software of claim 8, further operable to write the database log to the storage device in response to the database log being full.
 14. The software of claim 8, further operable to: receive information associated with a third database transaction; in response to the third transaction comprising a triggering event, log a third record of a fourth database transaction in a second log buffer substantially concurrently to the database log being written to the storage device; and write the first log buffer to the storage device up upon completion of the write of the database log to the storage device.
 15. The software of claim 8, wherein a total number of log buffers and a size for each of the log buffers is dynamically determined based on system usage.
 16. A system for logging database transactions, comprising: a memory storing a database, a database log, and a plurality of log buffers associated with the database log, each log buffer operable to store at least one log record associated with a database transaction, and the memory comprising a direct access storage device; and a processor operable to: log a first record of a first database transaction using the database log; write at least a portion of the database log to the storage device; and log a second record of a second database transaction in a first of the plurality of log buffers substantially concurrently to the database log being written to the storage device.
 17. The system of claim 16, the processor further operable to: receive information associated with a third database transaction; and in response to the first log buffer being full, log a third record of the third database transaction in a second of the plurality of log buffers substantially concurrently to the database log being written to the storage device.
 18. The system of claim 17, upon completion of the write of the database log to the storage device, the processor further operable to: receive information associated with a fourth database transaction; log a fourth record of the fourth database transaction in the database log; and write the first and second log buffers to the storage device using chained input/output.
 19. The system of claim 18, upon completion of the write of the first and second log buffers to the storage device, the processor further operable to free the first and second log buffers.
 20. The system of claim 16, the processor further operable to write the database log to the storage device in response to detecting a trigger event.
 21. The system of claim 16, the processor further operable to: receive information associated with a third database transaction; in response to the third transaction comprising a triggering event, log a third record of a fourth database transaction in a second of the plurality of log buffers substantially concurrently to the database log being written to the storage device; and write the first log buffer to the storage device up upon completion of the write of the database log to the storage device.
 22. The system of claim 16, wherein a total number of log buffers and a size for each of the plurality of log buffers is dynamically determined based on system usage. 